Using Group Subscription for CI #195
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates the CI workflows to use a group subscription for Azure API credentials. The changes enable workflows to be triggered by a new "ci-all" label and migrate all Azure API credential references from individual secrets to group subscription secrets.
- Added support for "ci-all" label to trigger workflows
- Updated Azure API credential references across all workflow files to use group subscription secrets
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| scripts/trigger_on_label.js | Added logic to trigger workflows when "ci-all" label is present |
| .github/workflows/tests-full.yml | Updated Azure API credentials to use group subscription secrets |
| .github/workflows/examples-spider.yml | Updated Azure API credentials to use group subscription secrets |
| .github/workflows/examples-compat.yml | Updated Azure API credentials to use group subscription secrets |
| .github/workflows/examples-calc-x.yml | Updated Azure API credentials to use group subscription secrets |
| .github/workflows/examples-apo.yml | Updated Azure API credentials to use group subscription secrets |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| core.notice( | ||
| `Triggering this workflow because pull request has the '${labelName}' label.` | ||
| ); | ||
| } else if (labels.includes("ci-all")) { |
There was a problem hiding this comment.
The hardcoded label 'ci-all' introduces duplication and reduces maintainability. Consider accepting this as a parameter or constant to maintain consistency with the existing labelName pattern used in the first condition.
No description provided.